Accessory authentication for electronic devices

ABSTRACT

Improved techniques to control utilization of accessory devices with electronic devices are disclosed. The improved techniques can use cryptographic approaches to authenticate electronic devices, namely, electronic devices that interconnect and communicate with one another. One aspect pertains to techniques for authenticating an electronic device, such as an accessory device. Another aspect pertains to provisioning software features (e.g., functions) by or for an electronic device (e.g., a host device). Different electronic devices can, for example, be provisioned differently depending on different degrees or levels of authentication, or depending on manufacturer or product basis. Still another aspect pertains to using an accessory (or adapter) to convert a peripheral device (e.g., USB device) into a host device (e.g., USB host). The improved techniques are particularly well suited for electronic devices, such as media devices, that can receive accessory devices. One example of a media device is a media player, such as a hand-held media player (e.g., music player), that can present (e.g., play) media items (or media assets).

CROSS-REFERENCES TO RELATED APPLICATIONS

This application, is a continuation of U.S. patent application Ser. No. 12/328,368, filed Dec. 4, 2008, which is a divisional of U.S. patent application Ser. No. 11/051,499, filed Feb. 3, 2005, entitled “ACCESSORY AUTHENTICATION FOR ELECTRONIC DEVICES,” now U.S. Pat. No. 7,823,214, which claims the benefit of U.S. provisional patent application No. 60/642,340, filed Jan. 7, 2005, entitled “ACCESSORY AUTHENTICATION FOR ELECTRONIC DEVICES,” which are incorporated by reference.

This application is also related to: (i) U.S. patent application Ser. No. 11/051,441, filed Feb. 3, 2005, entitled “SMALL MEMORY FOOTPRINT FAST ELLIPTIC ENCRYPTION,” which is hereby incorporated herein by reference; (ii) U.S. Provisional Patent Application No. 60/642,276, filed Jan. 7, 2005, entitled “PORTABLE MEDIA DEVICE AND IMPROVED PLAYLIST PROCESSING ON MEDIA DEVICES,” which is hereby incorporated herein by reference; (iii) U.S. Provisional Patent Application No. 60/642,334, filed Jan. 7, 2005, entitled “MEDIA MANAGEMENT FOR GROUPS OF MEDIA ITEMS,” which is hereby incorporated herein by reference; (iv) U.S. patent application Ser. No. 11/031,547, filed Jan. 7, 2005, entitled “PORTABLE POWER SOURCE TO PROVIDE POWER TO AN ELECTRONIC DEVICE VIA AN INTERFACE,” which is hereby incorporated herein by reference; (v) U.S. patent application Ser. No. 11/031,288, filed Jan. 7, 2005, entitled “METHOD AND SYSTEM FOR DISCOVERING A POWER SOURCE ON A PERIPHERAL BUS,” which is hereby incorporated herein by reference; (vi) U.S. patent application Ser. No. 29/220,463, filed Jan. 7, 2005, entitled “CONNECTOR SYSTEM,” which is hereby incorporated herein by reference; (vii) U.S. patent application Ser. No. 29/220,892, filed Jan. 7, 2005, entitled “CONNECTOR INTERFACE SYSTEM FOR MULTI-COMMUNICATION DEVICE,” which is hereby incorporated herein by reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to electrical devices and, more particularly, to electrical devices, such as media players, that receive accessory devices.

2. Description of the Related Art

A media player stores media assets, such as audio tracks or photos, that can be played or displayed on the media player. One example of a media player is the iPod® media player, which is available from Apple Computer, Inc. of Cupertino, Calif. Often, a media player acquires its media assets from a host computer that serves to enable a user to manage media assets. As an example, the host computer can execute a media management application to manage media assets. One example of a media management application is iTunes®, version 4.2, produced by Apple Computer, Inc.

A media player typically includes one or more connectors or ports that can be used to interface to the media player. For example, the connector or port can enable the media player to couple to a host computer, be inserted into a docking system, or receive an accessory device. There are today many different types of accessory devices that can interconnect to the media player. For example, a remote control can be connected to the connector or port to allow the user to remotely control the media player. As another example, an automobile can include a connector and the media player can be inserted onto the connector such that an automobile media system can interact with the media player, thereby allowing the media content on the media player to be played within the automobile.

Currently, the connectors or ports of a media player are open for use so long as a compatible connector or port is utilized. Consequently, numerous third-parties have developed accessory devices for use with other manufacturers' media players. One difficulty is that the manufacturer of a media player has no control over the various different accessory devices that can be connected to the media player. This is problematic because third-party accessory devices may be inferior, error-prone, disruptive (e.g., resource draining), or even damaging to the media player itself. Another problem is that third-party accessory devices which are unauthorized by the manufacturer of the media device may attempt to utilize features of the media device in an inappropriate or undesired manner.

Thus, there is a need for improved techniques to enable manufacturers of electronic devices to control the nature and extent to which accessory devices can be utilized with their electronic devices.

BRIEF SUMMARY OF THE INVENTION

Broadly speaking, the invention pertains to improved techniques to control utilization of accessory devices with electronic devices. The improved techniques can use cryptographic approaches to authenticate electronic devices, namely, electronic devices that interconnect and communicate with one another.

One aspect of the invention pertains to techniques for authenticating an electronic device, such as an accessory device. Another aspect of the invention pertains to provisioning software features (e.g., functions) by or for an electronic device (e.g., a host device). Different electronic devices can, for example, be provisioned differently depending on different degrees or levels of authentication, or depending on manufacturer or product basis. Still another aspect of the invention pertains to using an accessory (or adapter) to convert a peripheral device (e.g., USB device) into a host device (e.g., USB host). Embodiments of the invention may pertain to one or more of these aspects or other aspects disclosed herein.

The invention can be implemented in numerous ways, including as a method, system, device, apparatus (including graphical user interface), or computer readable medium. Several embodiments of the invention are discussed below.

As a portable electronic device, one embodiment of the invention includes at least: a media storage device that stores media content for one or more media items; a media presentation module that retrieves media content for at least one of the media items from the media storage and causes the media content to be presented for a user of the portable electronic device; an authentication table that stores authentication information for various accessory devices that are authorized to couple to and interact with the portable electronic device; and an authentication module that determines whether a particular accessory device that is coupled to the portable media device is authorized to interoperate with the portable electronic device based on at least a portion of the authentication information stored in the authentication table.

As an accessory device for a portable electronic device, one embodiment of the invention includes at least: an input/output port for interacting with the portable electronic device; an authentication algorithm; an authentication key associated with the accessory device;

an authentication controller, operatively connected to the input/output port, for performing authentication operations using at least the authentication algorithm and the authentication key; and accessory circuitry that performs operations associated with the accessory device.

As a connector for connecting an accessory device to a media player, one embodiment of the invention includes at least: a connector body; a plurality of electrical contacts attached within the connector body and serving to provide electrical connections between the accessory device and the media player; and a controller disposed in the connector body and providing an authentication key that allows the accessory device to be authenticated by the media player.

As a method for authorizing an accessory device for use with an electronic device, one embodiment of the invention includes at least the acts of: receiving a device identifier from the accessory device; receiving an authentication value from the accessory device; determining whether the accessory device is authentic based on the authentication value; and authorizing usage of the accessory device with the electronic device when it is determined that the accessory device is authentic.

As a method for authorizing an accessory device for use with an electronic device, another embodiment of the invention includes at least the acts of: detecting attachment of the accessory device with the electronic device; sending a random number to the accessory device after attachment of the accessory device has been detected; subsequently receiving an encoded value from the accessory device; receiving a device identifier from the accessory device; obtaining a cryptographic key based on the device identifier; decoding the encoded value using the cryptographic key to produce a decoded value; determining whether the decoded value corresponds to the random number; and authorizing usage of the accessory device with the electronic device when it is determined that the decoded value corresponds to the random number.

As a method for authorizing an accessory device for use with an electronic device, still another embodiment of the invention includes at least the acts of: detecting attachment of the accessory device with the electronic device; sending an authentication request, including at least a random number, to the accessory device after attachment of the accessory device has been detected; subsequently receiving an authentication response from the accessory device, the authentication response being in response to the authentication request, and the authentication response including at least an encoded value and a device identifier for the accessory device; obtaining a cryptographic key based on the device identifier; decoding the encoded value using the cryptographic key to produce a decoded value; and authorizing usage of the accessory device with the electronic device based on a correspondence between the decoded value and the random number.

As a method for authorizing an accessory device for use with an electronic device, still yet another embodiment of the invention includes at least the acts of: receiving a random number from the electronic device; encoding the random number using a cryptographic key provided within the accessory device, thereby producing an encoded value; and sending the encoded value and a device identifier to the electronic device.

As a method for controlling interaction between a media player and an accessory device, one embodiment of the invention includes at least the acts of: determining a classification of the accessory device; identifying an authorization level for the accessory device; and selectively activating features of the media device that are available to be used in conjunction with the accessory device based on the classification and authorization level of the accessory device.

As a media player system, one embodiment of the invention includes at least: a media player storing media content and supporting a plurality of predetermined functions, and an accessory device capable of connecting to the media player. The media player and the accessory device interact to perform an authentication process and, based on the authentication process, specific functions of the media device are selectively activated and thus available for use by the accessory device.

Other aspects and advantages of the invention will become apparent from the following detailed description taken in conjunction with the accompanying drawings which illustrate, by way of example, the principles of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention will be readily understood by the following detailed description in conjunction with the accompanying drawings, wherein like reference numerals designate like structural elements, and in which:

FIG. 1A is a block diagram of an accessory authentication system according to one embodiment of the invention.

FIG. 1B is a block diagram of an accessory authentication system according to another embodiment of the invention.

FIG. 1C is a block diagram of an accessory authentication system according to still another embodiment of the invention.

FIG. 2A is a block diagram of an authentication controller according to one embodiment of the invention.

FIG. 2B is a block diagram of an authentication manager according to one embodiment of the invention.

FIG. 3 is a block diagram of an authentication device according to one embodiment of the invention.

FIG. 4A is a flow diagram of a host authentication process according to one embodiment of the invention.

FIG. 4B is a flow diagram of an accessory authentication process according to one embodiment of the invention.

FIGS. 5A and 5B are flow diagrams of host device processing according to one embodiment of the invention.

FIGS. 6A and 6B are flow diagrams of accessory device processing according to one embodiment of the invention.

FIG. 6C is a diagram of an authorization table according to one embodiment of the invention.

FIGS. 7A and 7B are flow diagrams of an accessory device process according to one embodiment of the invention.

FIGS. 8A-8C are flow diagrams of a host device process according to one embodiment of the invention.

FIGS. 9A-9C are flow diagrams of an accessory device process according to one embodiment of the invention.

FIGS. 10A and 10B are flow diagrams of a host device process according to one embodiment of the invention.

FIG. 11 is a block diagram of a media management system according to one embodiment of the invention.

FIG. 12 is a block diagram of a media player according to one embodiment of the invention.

DETAILED DESCRIPTION OF THE INVENTION

The invention pertains to improved techniques to control utilization of accessory devices with electronic devices. The improved techniques can use cryptographic approaches to authenticate electronic devices, namely, electronic devices that interconnect and communicate with one another.

The improved techniques are particularly well suited for electronic devices, such as media devices, that can receive accessory devices. One example of a media device is a media player, such as a hand-held media player (e.g., music player), that can present (e.g., play) media items (or media assets). Examples of accessories for media devices, include: voice recorder, FM transceivers, peripheral bus devices (e.g., FireWire® devices or USB devices), media devices (e.g., media readers, displays, cameras, etc.), power units (e.g., power adapters, battery packs, etc.), speakers (headphones or speaker systems), remote control devices, network devices, or automobile integration units).

One aspect of the invention pertains to techniques for authenticating an electronic device, such as an accessory device. Another aspect of the invention pertains to provisioning software features (e.g., functions) by or for an electronic device (e.g., a host device). Different electronic devices can, for example, be provisioned differently depending on different degrees or levels of authentication, or depending on manufacturer or product basis. Still another aspect of the invention pertains to using an accessory (or adapter) to convert a peripheral device (e.g., USB device) into a host device (e.g., USB host). Embodiments of the invention may pertain to one or more of these aspects or other aspects disclosed herein.

Embodiments of the invention are discussed below with reference to FIGS. 1-12. However, those skilled in the art will readily appreciate that the detailed description given herein with respect to these figures is for explanatory purposes as the invention extends beyond these limited embodiments.

FIG. 1A is a block diagram of an accessory authentication system 100 according to one embodiment of the invention. The accessory authentication system 100 includes a mobile computing device 102. The mobile computing device 102 can also be referred to as a host device. Additionally, the mobile computing device 102 can, for example, pertain to a media player, a personal digital assistant, or a mobile telephone. The mobile computing device 102 includes a connector port 104 for receiving a connector.

The accessory authentication system 100 also includes an authentication device 106 having a connector 108 and a connector port 110. The authentication device 106 can be attached to the mobile computing device 102. In particular, when the authentication device 106 is attached to the mobile computing device 102, the connector 108 of the authentication device 106 is received by the connector port 104 of the mobile computing device 102. When the connector 108 is coupled into the connector port 104, the authentication device 106 is physically and electrically connected to the mobile computing device 102.

The accessory authentication system 100 further includes an accessory device 112. The accessory device 112 provides certain functionality to the mobile computing device 102 when the accessory device 112 is interconnected with the mobile computing device 102 via the authentication device 106. To facilitate such interconnection, the accessory device 112 includes a connector 114 and a cable 116. The cable 116 connects the connector 114 to the accessory device 112. The connector 114 can be coupled to the connector port 110 of the authentication device 106. When such connection has been made, the accessory device 112 is in electrical communication with the mobile computing device 102 via the authentication device 106.

Although the accessory authentication system 100 includes the connector 114 and the end of the cable 116, the connector 114 can be integrated into the accessory device 112. In other words, in another embodiment, the cable 116 is not needed.

According to one aspect of the invention, the authentication device 106 serves to authenticate itself to the mobile computing device 102. An authenticated device is deemed authorized to interact with the mobile computing device 102. Also, once authorized, the nature and degree of interaction between the authenticated device 106 (or the accessory device 102) and the mobile computing device 102 can be controlled. Consequently, once authorized, the mobile computing device 102 can consider the authentication device 106 to be a trusted partner which is permitted to access functions, features or operations of the mobile computing device 102. On the other hand, if the mobile computing device 102 determines that the authentication device 106 is not associated with a trusted partner, then the mobile computing device 102 can prevent or limit interactions with either the authentication device 106 for the accessory device 112. The authentication device 106 itself can also be considered an accessory device for the mobile computing device 102.

In one embodiment, the authentication device 106 serves as a bus interface adapter, such as a USB or FireWire® adapter. In such an embodiment, the authentication device 106 servers to adapt the mobile computing device 102 to a bus host device (e.g., USB or FireWire® host). The accessory device 112 then advantageously need only operate as a bus peripheral device (e.g., USB or FireWire® device).

FIG. 1B is a block diagram of an accessory authentication system 150 according to another embodiment of the invention. The accessory authentication system 150 includes a mobile computing device 152 having a connector port 154. The mobile computing device 152 can also be referred to as a host device. Additionally, the mobile computing device 152 can, for example, pertain to a media player, a personal digital assistant, or a mobile telephone.

The accessory authentication system 150 also includes an accessory device 156. The accessory device 156 includes a connector 158 and an authentication device 160. In this embodiment, the authentication device 160 in internal to the accessory device 156. The accessory device 156 can be coupled to the mobile computing device 152 by inserting the connector 158 into the connector port 154. One such connection is established, the accessory device 156 is electrically connected to the mobile computing device 152. Nevertheless, the mobile computing device 152 can interact with the authentication device 160 to enable the mobile computing device 152 to authenticate the accessory device 156. When authenticated, the accessory device 156 is deemed authorized to interact with the mobile computing device 152. Once authorized, the nature and degree of interaction between the accessory device 156 and the mobile computing device 152 can be controlled. Consequently, once authorized, the mobile computing device 152 can consider the accessory 156 to be a trusted partner (or associated with a trusted partner) which is permitted to access functions, features or operations of the mobile computing device 152. On the other hand, if the mobile computing device 152 determines that the accessory device 156 is not a trusted partner (or not associated with a trusted partner), then the mobile computing device 152 can prevent or limit interactions with the accessory device 156.

FIG. 1C is a block diagram of an accessory authentication system 170 according to still another embodiment of the invention. The accessory authentication system 170 includes a mobile computing device 172 having a connector port 174. The mobile computing device 172 can also be referred to as a host device. The mobile computing device 172 can, for example, pertain to a media player, a personal digital assistant, or a mobile telephone. The accessory authentication system 170 also includes an accessory device 176. The accessory device 176 includes a connector 178 and an authentication device 180. In this embodiment, the authentication device 180 in coupled to or integrated with the connector 178. The authentication device can be relatively small and thus by coupled to or integrated with the connector 178. By providing the authentication device 180 in the connector 178, an accessory device can easily be manufactured to provide authentication capabilities.

The accessory device 176 can be coupled to the mobile computing device 172 by inserting the connector 178 into the connector port 174. One such connection is established, the accessory device 176 is electrically connected to the mobile computing device 172. Nevertheless, the mobile computing device 172 can interact with the authentication device 180 to enable the mobile computing device 172 to authenticate the accessory device 176. When authenticated, the accessory device 176 is deemed authorized to interact with the mobile computing device 172. Once authorized, the nature and degree of interaction between the accessory device 176 and the mobile computing device 172 can be controlled. Consequently, once authorized, the mobile computing device 172 can consider the accessory 176 to be a trusted partner (or associated with a trusted partner) which is permitted to access functions, features or operations of the mobile computing device 172. On the other hand, if the mobile computing device 172 determines that the accessory device 176 is not a trusted partner (or not associated with a trusted partner), then the mobile computing device 172 can prevent or limit interactions with either the accessory device 172.

Additionally, although FIGS. 1A-1C reference authentication devices utilized to authenticate an accessory device for a mobile computing device, it should be understood that such authentication devices can alternatively be used to authenticate a mobile computing device for an accessory device. In any case, the authentication being performed is done in a secure manner, such as using cryptographic techniques. The cryptographic techniques not only serve to substantially prevent counterfeit accessory devices from being utilized, but also cause reduction in opportunities for “spoofing.” In one embodiment, the cryptographic techniques use a public-private key set to form a valid digital signature.

FIG. 2A is a block diagram of an authentication controller 200 according to one embodiment of the invention. The authentication controller 200 includes a processor 202, a Random Access Memory (RAM) 204, and a Read-Only Memory (ROM) 206. The ROM 206 includes a private key 208 and an authentication algorithm 210. The authentication controller 200 also receives a power line 212 and a communication bus (link) 214. For example, the power line 212 and the communication bus 214 can be provided by a connector of the authentication controller 200, such as the connector 108 illustrated in FIG. 1A, the connector 158 illustrated in FIG. 1B, or the connector 178 illustrated in FIG. 1C.

The processor 202 typically interacts with a mobile computing device (via the communication bus 214) to authenticate an accessory device (or an authentication device). During an authentication process, the processor 202 makes use of the authentication algorithm 210 as well as the private key 208 stored within the authentication controller 200. The authentication algorithm 210 can vary with different implementations, and suitable authentication algorithms are known to those skilled in the art.

Although not shown in FIG. 2A, the authentication controller 200, or an authentication device or accessory device including or utilizing the authentication controller 200, can further include a device identifier and additional circuitry. The device identifier can, for example, pertain to a product identifier and/or a manufacturer identifier. The additional circuitry can vary with implementation. When the additional circuitry is within an accessory device, the additional circuitry can be referred to as accessory circuitry.

In one embodiment, the authentication controller 200 is implemented on a single integrated circuit (i.e., single chip). By providing the authentication controller 200 on a single integrated circuit, external access to the private key 208 and the authentication algorithm 210 is substantially prevented. As a result, the authentication process is not only cryptographically secured but also physically secured by limited physical access.

FIG. 2B is a block diagram of an authentication manager 250 according to one embodiment of the invention. The authentication manager 250 is, for example, provided within an electronic device, such as the mobile computing device 102 illustrated in FIG. 1A, the mobile computing device 152 illustrated in FIG. 1B, or the mobile computing device 172 illustrated in FIG. 1C. In this embodiment, the authentication manager 250 of the electronic device authenticates an accessory device (or authentication device).

The authentication manager 250 includes an authentication module 252, an authorization table 254, and a port interface 256. The authentication module 252 operates to evaluate whether a particular accessory device (or authentication device) that couples to the port interface 256 is authentic and thus permitted to interoperate with the electronic device. The port interface 256 can provide power and a communication bus 258 to the accessory device (or authentication device). The authorization table 254 stores authentication information that is utilized by the authentication module 252 to evaluate whether certain accessory devices (or authentication devices) are authentic. As previously noted, the authentication manager 250 is provided within the electronic device, which can be referred to as a host device.

The electronic device (or host device) typically has various operating features that can be invoked or utilized. In one embodiment, an accessory device that is authenticated by the authentication manager 250 can have complete access to all of the features available on the electronic device (or host device). In another embodiment, the authorization table 254 can control the manner in which the features of the electronic device or host device that are made available to the accessory device. As an example, if the electronic device (or host device) offers a plurality of different features that can be utilized, the authorization table 254 can contain an indication as to which of these available features are permitted to be utilized by a particular accessory device. For example, authorization can be classified into levels or classes, each of which having different authorizations. The authorization can also specify the manner by which the different features are authorized for use. Hence, features may be authorized for use in limited ways. For example, a feature may be authorized for use over a slow communication interface (e.g., serial) with the electronic device and not over a fast communication interface (FireWire® or USB) with the electronic device. In other words, in this example, features may be authorized for use over only certain interface mechanisms.

FIG. 3 is a block diagram of an authentication device 300 according to one embodiment of the invention. In this embodiment, the authentication device 300 not only contains circuitry for authentication of itself or an accessory device coupled thereto, but also additional circuitry for providing other functions by the authentication device 300. In particular, the authentication device 300 is designed to couple to an electronic device as well as to an accessory device. As shown in FIG. 3, the authentication device 300 includes a controller 302 that includes memory 304. As an example, the controller 302 can pertain to the authentication controller 200 illustrated in FIG. 2A. The controller 302 can couple to a port connector 306 which in turn can connect to the electronic device. The port connector 306 can provide power from the electronic device to the controller 302 and a boost converter 308 over a power line (PIN). Additionally, the controller 302 can communicate with the electronic device through the port connector 306 by way of transmit and receive communication lines (TX, RX). Through such communication, the electronic device can determine whether the authentication device 300 is authorized for use with the electronic device. If the electronic device determines that the authentication device 300 is authorized, then the controller 302 can enable a boost converter 208 using an enable signal (EN). Once enabled, the boost converter 308, which receives an input voltage on the power line (PIN) from the port connector 306, can output a boosted output voltage on a power line (POUT) to a USB connector 310. For example, the input voltage can be 3.3 Volts and the boosted output voltage can be 5.0 Volts. The USB connector 310 also receives a pair of differential data lines (D+, D−) from the port connector 306 to allow data transmission between the electronic device and an accessory device that can be coupled to the USB connector 310.

In this embodiment, the authentication device 300 can operate to convert an electronic device into a host device, such as a USB host. Typically, the electronic device is a USB device, not a host device, but the attachment of the authentication device 300 to the electronic device can convert the electronic device into a host device. The host device can be USB compliant so that any USB device can be connected to the USB connector 310. In which case, any accessory with a USB port can connect with the electronic device via the authentication device 300.

The authentication techniques utilized by the invention can be utilized to allow a host device to authenticate an accessory device, or can allow an accessory device to authenticate a host device. The authentication process between the host device and the accessory device can be initiated at any time during coupling between the authentication device and the host device. For example, the authentication process can be initiated on connection of accessory device to host device, on first usage of restricted features, or periodically.

FIG. 4A is a flow diagram of a host authentication process 400 according to one embodiment of the invention. The host authentication process 400 is, for example, performed by a host device.

The host authentication process 400 initially receives 402 a device identifier associated with an accessory device to be authenticated. Additionally, an authentication value is received 404 from the accessory device. Here, the host device it is performing the authentication process; hence, the accessory device provides the authentication value to the host device. In one embodiment, in determining the authentication value, the accessory device utilizes a random number and a private key. The random number can be provided to the accessory device by the host device, or the random number can be available from the accessory device.

Next, the host authentication process 400 determines 406 whether the accessory device is authentic based on the authentication value and the device identifier. A decision 408 then determines whether the accessory device is authentic based on the determination made at block 406. When the decision 408 determines that the accessory device has been determined to be authentic, usage of the accessory device with the host device is authorized 410. The nature of the usage being authorized 410 can vary depending upon implementation. For example, the usage authorized 410 could allow complete usage of the accessory device or could allow limited usage of the accessory device.

On the other hand, when the decision 408 determines that the accessory device is not authentic, then the block 410 is bypassed such that the accessory device is not authorized for usage with the host device. In this case, since the accessory device was not determined to be authentic, usage of the accessory device with the host device is substantially restricted or prevented. Following the block 410, or its being bypassed, the host authentication process 400 is complete and ends.

FIG. 4B is a flow diagram of an accessory authentication process 450 according to one embodiment of the invention. The accessory authentication process 450 is, for example, performed by an accessory device.

The accessory authentication process 450 sends 452 a private key identifier associated with the accessory device to a host device. The private key identifier is used by the host device to obtain an appropriate private key which is used by the host device in producing the authentication value which is sent to the accessory device. The accessory device will receive 454 an authentication value from the host device.

Next, the accessory authentication process 450 determines 456 whether the host device is authentic based on the authentication value and a public key. Typically, the public key would be provided internal to the accessory device. A decision 458 then determines whether the host device has been determined to be authentic. When the decision 458 determines that the host device has been deemed authentic, then usage of the host device with the accessory device is authorized 460. The nature of the usage being authorized 460 can vary depending upon implementation. For example, the usage authorized 460 could allow complete usage of the host device or could allow limited usage of the host device.

On the other hand, when the decision 458 determines that the host device is not authentic, then the block 460 is bypassed, such that usage of the host device with the accessory device is substantially restricted or prevented. Following the block 460, or its being bypassed, the accessory authentication process 450 is complete and ends.

FIGS. 5A and 5B are flow diagrams of host device processing 500 according to one embodiment of the invention. The host device processing 500 is, for example, performed by an electronic device, such as the mobile computing device 152 illustrated in FIG. 1A, the mobile computing device 152 illustrated in FIG. 1B, or the mobile computing device 172.

The host device processing 500 begins with a decision 502 that determines whether authentication information has been received from an accessory device. When the decision 502 determines that authentication information has not been received, the host device processing 500 awaits receipt of authentication information. Once the decision 502 determines that authentication information has been received at the host device, the host device processing 500 continues. Namely, a random number is generated 504 at the host device. Typically, the random number is generated 504 at the host device in a random matter, such as using a random number generator. Next, an authentication request is sent 506 to the accessory device. Here, the authentication request includes at least a random number.

A decision 508 then determines whether an authentication response has been received from the accessory device. When the decision 508 determines that the authentication response has not yet been received, then the host device processing 500 awaits receipt of such an authentication response. Once the decision 508 determines that an authentication response has been received, an encoded number and a device identifier are extracted 510 from the authentication response.

Then, using the device identifier, a public key can be obtained 512. In one embodiment, the host device includes a plurality of public keys that are assigned to various different accessory devices. The device identifier, in such an embodiment, can be utilized to designate a particular accessory device and thus permit selection of an appropriate one of the public keys. Next, the encoded number is cryptographically decoded 514 using the public key to produce a decoded number. The decoded number is then compared 516 to the random number. In other words, the decoded number that is derived from the encoded number that was received in the authentication response from the accessory device is compared 516 with the random number that was previously sent to the accessory device in the authentication request. A decision 518 then determines whether the decoded number matches the random number. When the decision 518 determines that the decoded number does not match the random number, a user can optionally be notified 520 that the accessory device its unauthorized. Such a notification can be achieved by visual means or audio means. For example, a visual notification could be presented on a display device associated with the host device or the accessory device.

On the other hand, when the decision 518 determines that the decoded number does match the random number, authorized features associated with the device identifier are obtained 522. Then, utilization of the authorized features is enabled 524. Next, a decision 526 can determine whether the accessory device has been removed (or detached) from the host device. When the decision 526 that the accessory device has not been removed, then the host device processing 500 can continue to permit the utilization of the authorized features. However, once the decision 526 determines that the accessory device has been removed, the utilization of all features of the host device can be disabled 528. In other words, as an example, the authorized features can considered enabled for utilization during a session. The session can remain active so long as the accessory device remains attached to the host device. Once detached, the session ends and subsequent re-attachment requires re-authentication. Following the operation 528, as well as following the operation 520, the host device processing 500 is complete and ends.

FIGS. 6A and 6B are flow diagrams of accessory device processing 600 according to one embodiment of the invention. The accessory device processing 600 is, for example, performed by an accessory device, such as the accessory device 112 shown in FIG. 1A, the accessory device 156 shown in FIG. 1B, or the accessory device 176 shown in FIG. 1C. The accessory device processing 600 represents counterpart processing to the host device processing 500 illustrated in FIGS. 5A and 5B.

The accessory device processing 600 begins with a decision 602 that determines whether power is supplied to the accessory device. When the decision 602 determines that power is not supplied to the accessory device, the accessory device processing 600 awaits available power. Typically, power is supplied to the accessory device once the accessory device is connected to a host device. Hence, the decision 602 can alternatively determine whether the accessory device is connected to a host device.

Once the decision 602 determines that power is supplied to the accessory device, authentication information can be sent 604 to the host device. In one embodiment, the authentication information can include information indicating the one or more authentication versions that are supported. A decision 606 then determines whether an authentication request has been received. When the decision 606 determines that an authentication request is not been received, then the accessory device processing 600 awaits such a request. Once the decision 606 determines that an authentication request has been received, the random number provided in the authentication request is extracted 608. A private key is obtained 610 from the authentication device. For security reasons, the private key can be stored internal to the authentication device and not readily accessible outside of the authentication device. Next, the random number is cryptographically encoded 612 using key private key to produce an encoded number.

Thereafter, an authentication response is sent 614 to the host device. Here, the authentication response includes at least the encoded number and the device identifier. After the authentication response has been sent 614, a decision 616 determines whether access to features of the host device have been authorized. The decision 616 can be resolved actively or passively. For example, the host device might notify the accessory device that it has been authorized for access to one or more features of the host device. As another example, the host device may not notify the accessory device but might instead permit the accessory device to access the one or more features of the host device that are authorized. In any case, when the decision 616 determines that access to certain features on the host device have not been authorized, operation 620 of the accessory device, if any, is prevented from using the certain features of the host device. Indeed, in one embodiment, the host device can prevent any operation of the accessory device. As an example, the host device could prevent communication with the accessory device and/or cease supplying power to the accessory device.

On the other hand, when the decision 616 determines that access to certain features of the host device has been authorized, then the accessory device can be operated 618 in accordance with the authorized features. In other words, if authorized, the accessory device is able to interact with the host device to utilize the certain features supported by the host device.

Following the operations 618 and 620, a decision 622 determines whether the accessory device has been removed, i.e., whether the accessory device has been disconnected from the host device. When the decision 622 determines that the accessory device remains connected or attached to the host device, then the appropriate operations 618 or 620 can continue. Alternatively when the decision 622 determines that the accessory device has been removed, then the accessory device is no longer authorized to interact with the host device and thus can no longer utilized the previously authorized features supported by the host device. In this case, the accessory device processing 600 ends. However, the accessory device can be subsequently re-authorized by again performing the accessory device processing 600.

In the accessory device processing 600, the device identifier was provided with the authentication response. In an alternative embodiment, the device identifier can be provided to the host device differently, such as with the authentication information. The device identifier could also be separately provided to the host device.

FIG. 6C is a diagram of an authorization table 650 according to one embodiment of the invention. The authorization table is, for example, suitable for use as the authorization table 254 shown in FIG. 2B. In general, the authorization table 650 can be used to determine authorized features for a given accessory device. The authorization table 650 includes a device identifier column 652, a public key column 654, and an authorized features column 656. The authorization table 650 associates device identifiers, public keys and authorized features. Using a device identifier, the host device can determine an appropriate public key to be used when determining whether an accessory device identified using a particular device identifier can be authenticated. In the event that the authentication of the accessory device is successful, the authorized features associated with the device identifier can be identified in the authorized features column 656.

According to one aspect of the invention, a host device can operate to authenticate an accessory device being coupled to the host device. Those accessory devices that are able to be authenticated are permitted to interoperate with the host device to a greater extent. The host device can thus control the nature and degree by which accessory devices can interoperate with the host device. For example, the host device can limit, restrict or prevent accessory devices from interoperating with the host device when accessory devices are not able to be authenticated. Alternatively, the host device can enable greater interoperating with the host device when accessory devices are authenticated.

FIGS. 7A and 7B are flow diagrams of an accessory device process 700 according to one embodiment of the invention. FIGS. 8A-8C are flow diagrams of a host device process 800 according to one embodiment of the invention. The accessory device process 700 is performed by an accessory device during an authentication process with a host device. The host device process 800 is performed by the host device during the authentication process with the accessory process. The host device process 800 is a counterpart process to the accessory device process 700. In other words, during an authentication process, there is an exchange of information between the host device in the accessory device. Hence, FIGS. 7A and 7B represent processing performed by the accessory device and FIGS. 8A-8C represent processing performed by the host device, during one embodiment of an authentication process. It should be understood that although the authentication process depicted in these figures is illustrated as being substantially sequential, the authentication process can, in general, be considered a protocol utilized by an accessory device and a host device to exchange information for not only authentication but also subsequent operation. In one embodiment, such a protocol could be considered substantially parallel, such as in a client-server or master-slave implementation.

FIGS. 7A and 7B are flow diagrams of an accessory device process 700 according to one embodiment of the invention. The accessory device process 700 begins with a decision 702. The decision 702 determines whether an accessory device is connected to a host device. Typically, the decision 702 would detect the recent connection of the accessory device to the host device by way of a connector. In any case, when the decision 702 determines that the accessory device is not connected to the host device, the accessory device processing 700 can effectively await such a connection. In other words, the accessory device process 700 can be deemed invoked when the accessory device connects to the host device.

Once the decision 702 determines that the accessory device is connected to the host device, the accessory device process 700 continues. When the accessory device process 700 continues, authentication control information is sent 704 from the accessory device to the host device. As an example, the authentication control information can specify the type of accessory device, whether authentication is supported, when to authenticate, and/or power requirement of the accessory device. Specific examples of types of accessory devices are: microphone, simple remote, display remote, remote user interface, RF transmitter, and USB control host. The authentication status of the accessory device is cleared 706 on its on initiative or in response to a command or acknowledgement from the host device. Here, by clearing 706 the authentication status whenever an accessory device is connected, the accessory device can understand that it must be authenticated with the host device.

Next, a decision 710 determines whether a device authentication information request has been received. Here, the device authentication information request is sent to the accessory device by the host device. The device authentication information request serves to request certain information from the accessory device that will be utilized by the host device during the authentication process. When the decision 710 determines that a device authentication information request has not yet been received, the accessory device process 700 awaits such request. Once the decision 710 determines that a device authentication information request has been received, device authentication information is obtained 712 from the accessory device. As an example, the device authentication information can include a device identifier and a version indicator. The device identifier can pertain to a vendor identifier, a product identifier, or both. The version indicator can pertain to a protocol version that is supported. The device authentication information is then sent 714 the host device.

A decision 716 then determines whether an authentication request has been received from the host device. Here, the authentication request is a request from the host device to provide an authentication response containing a digital signature that is utilized to authenticate the accessory device. When the decision 716 determines that an authentication request has not been received, the accessory device process 700 awaits such request. Once the decision 716 determines that an authentication request has been received, a host random number is extracted 718 from the authentication request. The authentication request includes at least the host random number which is to be used in the authentication process.

A private key internal to the accessory device is then obtained 720. A device digital signature can then be calculated 722 using at least the host random number, the private key and a device random number. The device random number is generated or available within the accessory device. The device digital signature is an encrypted value that will be used by the host device to authenticate the accessory device. An authentication response is then sent 724 to the host device. The authentication response is formed such that it includes at least the device digital signature.

A decision 726 then determines whether device authentication status has been received from the host device. When the decision 726 determines that device authentication status has not been received, the accessory device process 700 awaits such information. Once the decision 726 determines that the device authentication status has been received, the device authentication status can be stored 728 on the accessory device. Following the block 728, the accessory device process 700 ends.

FIGS. 8A-8C are flow diagrams of a host device process 800 according to one embodiment of the invention. The host device process 800 begins with a decision 802 that determines whether authentication control information has been received from an accessory device. When the decision 802 determines that authentication control information has not been received, the host device process 800 awaits such information. Once the decision 802 determines that authentication control information has been received, the host device process 800 continues. In other words, the host device processing 800 is effectively invoked once authentication control information is received.

When the host device process 800 continues, the device authentication status can be reset (i.e., cleared) 804. Thus, the accessory device is deemed unauthentic until the authentication process is able to authenticate the accessory device. This operation may have already occurred automatically at the host device, such as when an accessory device is disconnected from the host device.

A decision 806 then determines whether the accessory device supports authentication based on the authentication control information. When the decision 806 determines that authentication is not supported by the accessory device, the host device processing 800 ends without having authenticated the accessory device. In this case, the accessory device may be restricted, even prevented, from interoperating with the host device.

On the other hand, when the decision 806 determines that authentication is supported by the accessory device, the host device process 800 continues. At this point, a device authentication information request is sent 808 to the accessory device. A decision 810 then determines whether device authentication information has been received. When the decision 810 determines that device authentication information has not been received, the host device process 800 awaits such information is received. Once the decision 810 determines that device authentication information has been received, a decision 812 determines whether authentication should be performed at this time. Here, it should be understood that the host device process 800 can perform authentication proximate to when the accessory device is connected to the host device, or the authentication can be deferred until a later point in time, such as periodically when the accessory device desires (e.g., first desires) to use extended features of the host device which are only available to an authenticated device. Hence, when the decision 812 determines that authentication is not immediately required, the host device process 800 can await the appropriate time to perform the authentication process. Once the decision 812 determines that authentication should be performed, a host random number is generated 814. Next, an authentication request is sent 816 to the accessory device. The authentication request includes at least the host random number that has been generated 814.

A decision 818 then determines whether an authentication response has been received from the accessory device. When the decision 818 determines that an authentication response has been received, a device digital signature is extracted 820 from the authentication response.

A public key is also obtained 822 for use with the accessory device. In one embodiment, the host device includes a plurality of public keys that are associated with different device identifiers. Hence, the device authentication information from the accessory device can include a device identifier for the accessory device. The device identifier can be utilized in obtaining 822 the public key for use with the accessory device. As an example, an authentication table, such as the authentication table 650 shown in FIG. 6C, can be used to obtain the public key.

Next, the device digital signature is validated 824 using the public key. In one embodiment, the validation 824 of the digital device signature also makes use of the host random number. A decision 826 then determines whether the digital device signature has been validated. When the decision 826 determines that the device digital signature has been validated, the accessory device is deemed 828 authentic. Command access permissions associated with the accessory device can then be updated 830 so that the host device permits the accessory device to use those commands that are permitted by authenticated devices. On the other hand, when the decision 826 determines that the digital device signature has not been validated, the accessory device is deemed 832 not authentic. Following the blocks 830 and 832, device authentication status is sent 834 to the accessory device. The device authentication status serves to inform the accessory device as to whether or not the host device has authenticated the accessory device.

It the device authentication status indicates that the accessory device is deemed authentic, then the accessory device can proceed to interact with the host device in accordance with an authorized degree of the usage. As another example, when the device authentication status indicates that the accessory device is deemed not authentic, then the accessory device can be restricted, even prevented, from interaction with the host device. In any case, the authorized degree of usage of the accessory device with the host device is greater when the accessory device is deemed authentic.

FIGS. 9A-9C are flow diagrams of an accessory device process 900 according to one embodiment of the invention. FIGS. 10A and 10B are flow diagrams of a host device process 1000 according to one embodiment of the invention. The accessory device process 900 is performed by an accessory device during an authentication process when seeking to authenticate a host device. The host device process 1000 is performed by the host device during the authentication process with the accessory process. The host device process 1000 is a counterpart process to the accessory device process 900. In other words, during an authentication process, there is an exchange of information between the host device in the accessory device. Hence, FIGS. 9A-9C represent processing performed by the accessory device and FIGS. 10A and 10B represent processing performed by the host device, during one embodiment of an authentication process. It should be understood that although the authentication process depicted in these figures is illustrated as being substantially sequential, the authentication process can be considered a protocol utilized by an accessory device and a host device to exchange information for not only authentication but also subsequent operation. In one embodiment, such a protocol could be considered substantially parallel, such as in a client-server or master-slave implementation.

FIGS. 9A-9C are flow diagrams of an accessory device process 900 according to one embodiment of the invention. The accessory device process 900 is performed by an accessory device when seeking to authenticate a host device connected with the accessory device.

The accessory device process 900 begins with a decision 902 that determines whether the accessory device is connected to the host device. When the decision 902 determines that the accessory device is not connected to the host device, the accessory device process 900 awaits such a connection. In other words, the accessory device process 900 is effectively invoked when the accessory device is connected to the host device. In one embodiment, the accessory device 900 is invoked once it is determined that an accessory device has just recently connected to the host device. However, in other embodiments, the authentication process can be performed later (e.g., deferred).

Once the decision 902 determines that the accessory device is connected to the host device, authentication control information is sent 904 to the host device. A decision 906 then determines whether the authentication control information has been acknowledged. When the decision 906 determines that the authentication control information has been acknowledged, authentication status of the accessory device can be cleared 908. Here, by clearing 908 the authentication status, whenever the host device is connected, it is authenticated by the accessory device.

Next, a host authentication information request is sent 910 to the host device. A decision 912 then determines whether host authentication information has been received from the host device. When the decision 912 determines that host authentication information has not been received from the host device, the accessory device process 900 awaits such information.

Once the decision 912 determines that the host authentication information has been received, a decision 914 determines whether authentication should be performed at this time. Here, it should be noted that the authentication process can be performed immediately, such as soon after the connection has been detected, or can be deferred until a later point in time, such as when commands or extended functionality of the host device are requested. In any case, when the decision 914 determines that authentication is not to be performed at this time, the accessory device process 900 can await the appropriate time to performed the authentication.

Once the decision 914 determines that authentication should be performed, a device random number is generated 916. Then, an authentication request is sent 918 to the host device. The authentication request typically includes at least the device random number and a private key number. The private key number is used to select a private key at the host device.

Next, a decision 920 determines whether an authentication response has been received from the host device. When the decision 920 determines that an authentication response has not been received, then the accessory device process 900 awaits such a response. Once the decision 920 determines that an authentication response has been received, a host digital signature is extracted 922 from the authentication response. Also, a public key is obtained 924 based on a public key index. In one embodiment, the public key index is provided to the accessory device with the host authentication information. In one embodiment, the public key is determined at the accessory device using the public key index. For example, the accessory device can include a plurality of different public keys, and the appropriate one of the public keys to be utilized can be identified by the public key index.

The host digital signature is then validated 926 using the public key. The validation 926 may also make use of the device random number. Thereafter, a decision 928 determines whether the host digital signature has been validated. When the decision 928 determines that the host digital signature has been validated, the host device is deemed 930 to be authentic. Consequently, command access permissions for use by the host device are updated 932. For example, since the host device is validated, the interaction between the host device and the accessory device is deemed authorized, at least to the extent of the command access permissions. Alternatively, when the decision 928 determines that the host device is not validated, the host device is deemed 934 to be not authentic. Following the blocks 932 and 934, host authentication status can be sent 936 to the host device. Here, the host authentication status informs the host device of the results of the authentication process. Following the blocks 936, the accessory device process 900 is complete and ends.

FIGS. 10A and 10B are flow diagrams of host device processing 1000 according to one embodiment of the invention. The host device processing 1000 is performed on a host device while interacting with an accessory device. The host device processing 1000 represents counterpart processing to the accessory device process 900 during an authentication process.

The host device processing 1000 begins with a decision 1002 that determines whether authentication control information from the accessory device has been received. When the decision 1002 determines that authentication control information has not been received, the host device processing 1000 awaits such information. Once the decision 1002 determines that authentication control information has been received, the host device processing 1000 continues. In other words, the host device processing 1000 is effectively invoked once authentication control information from the accessory device is received.

When the host device processing 1000 continues, the host authentication status is reset 1004, thereby clearing any prior authentication status it may have. Then, a decision 1006 determines whether a host authentication information request has been received. When the decision 1006 determines that a host authentication information request has not been received, the host device processing 1000 awaits such request. Once the decision 1006 determines that a host authentication information request has been received, host authentication information is obtained 1008 at the host device. The host authentication information is then send 1010 to the accessory device. In one embodiment, the host authentication information includes at least version information and a public key index.

Next, a decision 1012 determines whether an authentication request has been received. When the decision 1012 determines that an authentication request has not been received, the host device processing 1000 awaits such request. Once the decision 1012 determines that an authentication request has been received, the device random number and a private key number are extracted 1014 from the authentication request. In this embodiment, it is understood that the authentication request being received from the accessory device includes at least the device random number and the private key number that can be utilized by the host device. Then, a private key is obtained 1016 based on the private key number. Here, the private key being obtained 1016 is internal to the host device and identified through use of the private key number.

A host digital signature is then calculated 1018 using the device random number, the private key and a host random number. The host random number can be generated or available at the host device. The host device process 1000 then sends 1020 an authentication response to the accessory device. The authentication response includes at least the host digital signature.

Thereafter, a decision 1022 determines whether a host authentication status has been received. When the decision 1022 determines that the host authentication status has not been received, the host device processing 1000 awaits such information. Once the decision 1022 determines that the host authentication status has been received, the authentication status is stored 1024 at the host device. At this point, the host device understands the authentication status it has with the accessory device and can operate accordingly. Following the block 1024, the host device processing 1000 is complete and ends.

According to another aspect of the invention, an electronic device, or host device, can also connect to a host computer, such as a personal computer. The personal computer can store, utilize and manage media items. The management of the media items can be not only for the host computer but also for the electronic device.

FIG. 11 is a block diagram of a media management system 1100 according to one embodiment of the invention. The media management system 1100 includes a host computer 1102 and a media player 1104. The host computer 1102 is typically a personal computer. The host computer, among other conventional components, includes a management module 1106 which is a software module. The management module 1106 provides for centralized management of media items (and/or playlists) not only on the host computer 1102 but also on the media player 1104. More particularly, the management module 1106 manages those media items stored in a media store 1108 associated with the host computer 1102. The management module 1106 also interacts with a media database 1110 to store media information associated with the media items stored in the media store 1108.

The media information pertains to characteristics or attributes of the media items. For example, in the case of audio or audiovisual media, the media information can include one or more of: title, album, track, artist, composer and genre. These types of media information are specific to particular media items. In addition, the media information can pertain to quality characteristics of the media items. Examples of quality characteristics of media items can include one or more of: bit rate, sample rate, equalizer setting, volume adjustment, start/stop and total time.

Still further, the host computer 1102 includes a play module 1112. The play module 1112 is a software module that can be utilized to play certain media items stored in the media store 1108. The play module 1112 can also display (on a display screen) or otherwise utilize media information from the media database 1110. Typically, the media information of interest corresponds to the media items to be played by the play module 1112.

The host computer 1102 also includes a communication module 1114 that couples to a corresponding communication module 1116 within the media player 1104. A connection or link 1118 removably couples the communication modules 1114 and 1116. In one embodiment, the connection or link 1118 is a cable that provides a data bus, such as a FIREWIRE® bus or USB bus, which is well known in the art. In another embodiment, the connection or link 1118 is a wireless channel or connection through a wireless network. Hence, depending on implementation, the communication modules 1114 and 1116 may communicate in a wired or wireless manner.

The media player 1104 also includes a media store 1120 that stores media items within the media player 1104. Optionally, the media store 1120 can also store data, i.e., non-media item storage. The media items being stored to the media store 1120 are typically received over the connection or link 1118 from the host computer 1102. More particularly, the management module 1106 sends all or certain of those media items residing on the media store 1108 over the connection or link 1118 to the media store 1120 within the media player 1104. Additionally, the corresponding media information for the media items that is also delivered to the media player 1104 from the host computer 1102 can be stored in a media database 1122. In this regard, certain media information from the media database 1110 within the host computer 1102 can be sent to the media database 1122 within the media player 1104 over the connection or link 1118. Still further, playlists identifying certain of the media items can also be sent by the management module 1106 over the connection or link 1118 to the media store 1120 or the media database 1122 within the media player 1104.

Furthermore, the media player 1104 includes a play module 1124 that couples to the media store 1120 and the media database 1122. The play module 1124 is a software module that can be utilized to play certain media items stored in the media store 1120. The play module 1124 can also display (on a display screen) or otherwise utilize media information from the media database 1122. Typically, the media information of interest corresponds to the media items to be played by the play module 1124.

According to one embodiment, to support an authentication process on the media player 1104, the media player 1104 can further include an authentication module 1126 and an authentication table 1128. In one implementation, the authentication module 1126 and the authentication table 1128 can respectively correspond to the authentication module 252 and the authentication table 254 described above with reference to FIG. 2B.

As previously noted, an accessory device can couple to a media player. Hence, FIG.

11 also illustrates an accessory device 1130 capable of coupling to the media player 1104. According to one embodiment, the accessory device 1130 can further include an authentication device 1132. The authentication device 1132 operates to support the authentication process on the media player 1104 according to one embodiment. In one implementation, the authentication device 1132 can correspond to the authentication controller 200 described above with reference to FIG. 2A.

In one embodiment, the media player 1104 has limited or no capability to manage media items on the media player 1104. However, the management module 1106 within the host computer 1102 can indirectly manage the media items residing on the media player 1104. For example, to “add” a media item to the media player 1104, the management module 1106 serves to identify the media item to be added to the media player 1104 from the media store 1108 and then causes the identified media item to be delivered to the media player 1104. As another example, to “delete” a media item from the media player 1104, the management module 1106 serves to identify the media item to be deleted from the media store 1108 and then causes the identified media item to be deleted from the media player 1104. As still another example, if changes (i.e., alterations) to characteristics of a media item were made at the host computer 1102 using the management module 1106, then such characteristics can also be carried over to the corresponding media item on the media player 1104. In one implementation, the additions, deletions and/or changes occur in a batch-like process during synchronization of the media items on the media player 1104 with the media items on the host computer 1102.

In another embodiment, the media player 1104 has limited or no capability to manage playlists on the media player 1104. However, the management module 1106 within the host computer 1102 through management of the playlists residing on the host computer can indirectly manage the playlists residing on the media player 1104. In this regard, additions, deletions or changes to playlists can be performed on the host computer 1102 and then by carried over to the media player 1104 when delivered thereto.

As previously noted, synchronization is a form of media management. The ability to automatically initiate synchronization was also previously discussed above and in the related application noted above. Still further, however, the synchronization between devices can be restricted so as to prevent automatic synchronization when the host computer and media player do not recognize one another.

According to one embodiment, when a media player is first connected to a host computer (or even more generally when matching identifiers are not present), the user of the media player is queried as to whether the user desires to affiliate, assign or lock the media player to the host computer. When the user of the media player elects to affiliate, assign or lock the media player with the host computer, then a pseudo-random identifier is obtained and stored in either the media database or a file within both the host computer and the media player. In one implementation, the identifier is an identifier associated with (e.g., known or generated by) the host computer or its management module and such identifier is sent to and stored in the media player. In another implementation, the identifier is associated with (e.g., known or generated by) the media player and is sent to and stored in a file or media database of the host computer.

FIG. 12 is a block diagram of a media player 1200 according to one embodiment of the invention. The media player 1200 includes a processor 1202 that pertains to a microprocessor or controller for controlling the overall operation of the media player 1200. The media player 1200 stores media data pertaining to media items in a file system 1204 and a cache 1206. The file system 1204 is, typically, a storage device. The file system 1204 typically provides high capacity storage capability for the media player 1200. For example, the storage device can be semiconductor-based memory, such as FLASH memory. The file system 1204 can store not only media data but also non-media data (e.g., when operated in a data mode). However, since the access time to the file system 1204 is relatively slow, the media player 1200 can also include a cache 1206. The cache 1206 is, for example, Random-Access Memory (RAM) provided by semiconductor memory. The relative access time to the cache 1206 is substantially shorter than for the file system 1204. However, the cache 1206 does not have the large storage capacity of the file system 1204. Further, the file system 1204, when active, consumes more power than does the cache 1206. The power consumption is often a concern when the media player 1200 is a portable media player that is powered by a battery (not shown). The media player 1200 also includes a RAM 1220 and a Read-Only Memory (ROM) 1222. The ROM 1222 can store programs, utilities or processes to be executed in a non-volatile manner. The RAM 1220 provides volatile data storage, such as for the cache 1206. In one embodiment, the ROM 1220 and the RAM 1222 can be provided by the storage device providing the file system 1204.

The media player 1200 also includes a user input device 1208 that allows a user of the media player 1200 to interact with the media player 1200. For example, the user input device 1208 can take a variety of forms, such as a button, keypad, dial, etc. Still further, the media player 1200 includes a display 1210 (screen display) that can be controlled by the processor 1202 to display information to the user. The user input device 1208 and the display 1210 can also be combined in the case of a touch screen. A data bus 1211 can facilitate data transfer between at least the file system 1204, the cache 1206, the processor 1202, and the CODEC 1212.

In one embodiment, the media player 1200 serves to store a plurality of media items (e.g., songs) in the file system 1204. When a user desires to have the media player play a particular media item, a list of available media items is displayed on the display 1210. Then, using the user input device 1208, a user can select one of the available media items. The processor 1202, upon receiving a selection of a particular media item, supplies the media data (e.g., audio file) for the particular media item to a coder/decoder (CODEC) 1212. The CODEC 1212 then produces analog output signals for a speaker 1214. The speaker 1214 can be a speaker internal to the media player 1200 or external to the media player 1200. For example, headphones or earphones that connect to the media player 1200 would be considered an external speaker.

The media player 1200 also includes a network/bus interface 1216 that couples to a data link 1218. The data link 1218 allows the media player 1200 to couple to a host computer or to accessory devices. The data link 1218 can be provided over a wired connection or a wireless connection. In the case of a wireless connection, the network/bus interface 1216 can include a wireless transceiver.

In one implementation, the host computer can utilize an application resident on the host computer to permit utilization and provide management for playlists, including a media device playlist. One such application is iTunes®, version 4.2, produced by Apple Computer, Inc. of Cupertino, Calif.

The media items (media assets) can pertain to one or more different types of media content. In one embodiment, the media items are audio tracks. In another embodiment, the media items are images (e.g., photos). However, in other embodiments, the media items can be any combination of audio, graphical or video content.

The above discussion makes reference to random number used with cryptographic approaches to authenticate an accessory device or a host device. The cryptographic approaches discussed above can make use of random numbers, public-private key pairs and authentication algorithms. The random numbers can also be referred to as random digests. The public-private key pairs and authentication algorithms can utilize public-key cryptographic systems, such as the well known RSA algorithm or an Elliptic Curve Cryptography (ECC) algorithm. It may be advantageous to use an ECC algorithm that offers reduced memory consumption with relatively smaller keys (e.g., 160 bits) as compared to larger keys (e.g., 1024 bits) as is typical for RSA implementations. An example of a reduced memory ECC algorithm is described in the related U.S. patent application Ser. No. 11/051,441, filed Feb. 3, 2005, entitled “SMALL MEMORY FOOTPRINT FAST ELLIPTIC ENCRYPTION,” which has been incorporated herein by reference.

The various aspects, embodiments, implementations or features of the invention can be used separately or in any combination.

The invention can be implemented by software, hardware, or a combination of hardware and software. The invention can also be embodied as computer readable code on a computer readable medium. The computer readable medium is any data storage device that can store data which can thereafter be read by a computer system. Examples of the computer readable medium include read-only memory, random-access memory, CD-ROMs, DVDs, magnetic tape, optical data storage devices, and carrier waves. The computer readable medium can also be distributed over network-coupled computer systems so that the computer readable code is stored and executed in a distributed fashion.

The advantages of the invention are numerous. Different aspects, embodiments or implementations may yield one or more of the following advantages. One advantage of the invention is that control over accessory interaction with a host device can be controlled. As a result, an electronic device can limit usage of some or all of its features to only those accessory devices that are deemed authorized. Another advantage of the invention is that it provides the ability to manage quality of those accessory device that are permitted to be utilized with host devices. By managing quality of accessory devices, the operation of an electronic device is less likely tarnished by the attachment of an inferior accessory device. Still another advantage of the invention is that an authentication process can control access to certain features of electronic devices on a manufacturer or device basis.

The many features and advantages of the present invention are apparent from the written description and, thus, it is intended by the appended claims to cover all such features and advantages of the invention. Further, since numerous modifications and changes will readily occur to those skilled in the art, the invention should not be limited to the exact construction and operation as illustrated and described. Hence, all suitable modifications and equivalents may be resorted to as falling within the scope of the invention. 

1-5. (canceled)
 6. An electronic system comprising: an accessory comprising: a first memory to store a device identifier and to provide the device identifier; a processor coupled to the memory to receive the device identifier from the first memory and to provide the device identifier to a communication bus; and a connector to provide a path for the communication bus; and a mobile computing device comprising: a connector to provide a path for the communication bus; a port interface coupled to the connector to receive the device identifier from the accessory over the communication bus; an authorization table comprising a list of device identifiers and corresponding sets of authorized features; and an authentication module coupled to the port interface to receive the device identifier from the accessory, the authorization module further coupled to the authorization table to find a match for the device identifier from the accessory in the list of device identifiers and to find a corresponding set of authorized features, and then to allow the accessory to access features of the mobile computing device identified by the corresponding set of authorized features.
 7. The electronic system of claim 6 wherein when the accessory does not provide a device identifier to the mobile computing device, the mobile computing device allows the accessory access to a limited set of features of the mobile computing device.
 8. The electronic system of claim 6 wherein the authorization table comprises a first device identifier corresponding to a first manufacturer, along with a corresponding first set of authorized features, and a second device identifier corresponding to a second manufacturer, along with a corresponding second set of authorized features, wherein the first set of authorized features is different than the second set of authorized features.
 9. The electronic system of claim 6 wherein the device identifier from the accessory identifies a manufactures of the accessory.
 10. The electronic system of claim 6 wherein the first memory further stores a private key and the authorization table further comprises a public key for each of the device identifiers in the list of device identifiers.
 11. The electronic system of claim 6 wherein the connector on the mobile computing device connects to the connector on the accessory through a cable.
 12. The electronic system of claim 11 wherein the port interface provides power to the accessory.
 13. An accessory comprising: a first memory to store a device identifier and to provide the device identifier; a processor coupled to the memory to receive the device identifier from the first memory and to provide the device identifier to a communication bus; and a connector to provide a path for the communication bus to provide the device identifier from the accessory to a mobile computing device, the device identifier from the accessory usable by an authorization module in the mobile computing device to find a match for the device identifier from the accessory in a list of device identifiers in an authorization table and to find a corresponding set of authorized features in the authorization table, and then to allow the accessory to access the corresponding set of authorized features.
 14. The accessory of claim 13 wherein when the accessory does not provide a device identifier to the mobile computing device, the mobile computing device allows the accessory access to a limited set of features.
 15. The accessory of claim 13 wherein the authorization table comprises a first device identifier corresponding to a first manufacturer, along with a corresponding first set of authorized features, and a second device identifier corresponding to a second manufacturer, along with a corresponding second set of authorized features, wherein the first set of authorized features is different than the second set of authorized features.
 16. The accessory of claim 13 wherein the device identifier provided by the accessory identifies a manufactures of the accessory.
 17. The accessory of claim 13 wherein the first memory further stores a private key and the authorization table further comprises a public key for each of the device identifiers in the list of device identifiers.
 18. The accessory of claim 13 wherein a connector on the mobile computing device connects to the connector on the accessory through a cable.
 19. The accessory of claim 18 wherein the accessory receives power from the mobile computing device.
 20. A mobile computing device comprising: a connector to provide a path for the communication bus; a port interface coupled to the connector to receive a device identifier from the accessory over the communication bus; an authorization table comprising a list of device identifiers and a corresponding set of authorized features; and an authentication module coupled to the port interface to receive the device identifier from the accessory, the authorization module further coupled to the authorization table to find a match for the device identifier from the accessory in the list of device identifiers and to find a corresponding set of authorized features, and then to allow the accessory to access the corresponding set of authorized features.
 21. The mobile computing device of claim 20 wherein when the accessory does not provide a device identifier to the mobile computing device, the mobile computing device allows the accessory access to a limited set of features.
 22. The mobile computing device of claim 20 wherein the authorization table comprises a first device identifier corresponding to a first manufacturer, along with a corresponding first set of authorized features, and a second device identifier corresponding to a second manufacturer, along with a corresponding second set of authorized features, wherein the first set of authorized features is different than the second set of authorized features.
 23. The mobile computing device of claim 20 wherein the device identifier from the accessory identifies a manufactures of the accessory.
 24. The mobile computing device of claim 20 wherein the authorization table further comprises a public key for each of the device identifiers in the list of device identifiers.
 25. The mobile computing device of claim 20 wherein the connector on the mobile computing device connects to a connector on the accessory through a cable. 